micro_utils.dokka/dev.inmo.micro_utils.fsm.common/[jvm]DefaultStatesMachine

DefaultStatesMachine

open class DefaultStatesMachine<T : State>(statesManager: StatesManager<T>, handlers: List<CheckableHandlerHolder<in T, T>>) : StatesMachine<T>

Default realization of StatesMachine. It uses statesManager for incapsulation of States storing and contexts resolving, and uses launchStateHandling for State handling.

This class suppose to be extended in case you wish some custom behaviour inside of launchStateHandling, for example

Constructors

fun <T : State> DefaultStatesMachine(statesManager: StatesManager<T>, handlers: List<CheckableHandlerHolder<in T, T>>)

Functions

handleState

open suspend override fun StatesMachine<in T>.handleState(state: T): T?

Will call launchStateHandling for state handling

launchStateHandling

open suspend fun launchStateHandling(state: T, handlers: List<CheckableHandlerHolder<in T, T>>): T?

performStateUpdate

open suspend fun performStateUpdate(previousState: Optional<T>, actualState: T, scope: CoroutineScope)

start

open override fun start(scope: CoroutineScope): Job

Launch handling of states. On statesManager, statesManager will be called lambda with performing of state. If launchStateHandling will returns some State then statesManager will be used, otherwise StatesManager.endChain.

startChain

open suspend override fun startChain(state: T)

Just calls StatesManager.startChain of statesManager

Inheritors

DefaultUpdatableStatesMachine